src/run.ts (1)

98-160: 💡 Verification agent

🧩 Analysis chain

Verify the tag format is consistent with changesets behavior.

The implementation assumes tag format is packageName@version, but for certain repository types, changesets might generate different formats. Please ensure consistency with how changesets generates its tags.

---

🌐 Web query:

How does changesets format its Git tags for single-package vs multi-package repositories?

💡 Result:

Changesets formats Git tags differently depending on whether they're used in single-package or multi-package repositories:

Single-package repositories

• Tags follow the format vX.Y.Z (e.g., v1.2.3)
• Includes a "v" prefix before the semantic version[1][2][6]

Multi-package repositories

• Tags use package-name@X.Y.Z format (e.g., utils@1.0.0)
• Combines the package name with its version number[2][6][8]

Repository Type	Tag Format Example
Single-package	v1.2.3
Multi-package (monorepo)	my-package@1.0.0

This distinction ensures clear version tracking in monorepos while maintaining conventional version tagging for standalone packages. The tags are automatically generated during the changeset publish command, and Changesets handles dependency-aware versioning in monorepos by:

1. Updating interdependent package versions when needed[3][6]
2. Creating separate tags for each modified package[5][10]

For both repository types, you must manually push tags using git push --follow-tags after publishing[2][8]. The version numbers themselves are determined from package.json files, which Changesets updates during the version command[1][6].

Citations:

• 1: https://brianschiller.com/blog/2023/09/18/changesets-vs-semantic-release/
• 2: https://github.com/changesets/changesets/blob/main/docs/command-line-options.md
• 3: https://dev.to/ramunarasinga-11/manage-your-versioning-and-changelogs-using-changesets-4big
• 4: https://insights.sei.cmu.edu/blog/versioning-with-git-tags-and-conventional-commits/
• 5: https://infinum.com/handbook/frontend/changesets
• 6: https://github.com/changesets/changesets/blob/main/packages/cli/README.md
• 7: https://www.jetbrains.com/help/rider/Tagging_Changesets.html
• 8: https://www.npmjs.com/package/@changesets/cli
• 9: https://changesets-docs.vercel.app/en/prereleases
• 10: https://lirantal.com/blog/introducing-changesets-simplify-project-versioning-with-semantic-releases
• 11: https://www.finalbuilder.com/forums/t/changesets-dont-detect-tag-changes-in-submodules/6676
• 12: https://github.com/changesets/changesets
• 13: changesets/changesets#972

---

Action: Align single-package tag format with Changesets behavior

In the single-package branch (tool === 'root'), the current code pushes tags in the format packageName@version (e.g., my-package@1.2.3), while Changesets for single-package repositories generate tags with a v prefix (e.g., v1.2.3). This leads to inconsistency since the GitLab release call correctly uses v${pkg.packageJson.version}. Please update the push tag logic in the single-package branch to use the vX.Y.Z format.

• Change the tag pushed in the tool === 'root' branch to use v${pkg.packageJson.version}.
• Verify that the regex and tag-naming logic in the multi-package branch remain correct.

src/run.ts (1)

120-124: 💡 Verification agent

🧩 Analysis chain

Consider using v${pkg.packageJson.version} for single-package repositories.

For single package repositories, the tag should be only vx.y.z format instead of packageName@version.

---

🏁 Script executed:

#!/bin/bash
# Check if this is a single-package or multi-package repository
# by looking at the package.json files in the repository

echo "Checking repository structure..."
# Count package.json files (excluding node_modules)
PACKAGE_COUNT=$(find . -name "package.json" -not -path "*/node_modules/*" -not -path "*/dist/*" -not -path "*/build/*" | wc -l)
echo "Found $PACKAGE_COUNT package.json files"

# If it's just one, it's likely a single-package repo
if [ "$PACKAGE_COUNT" -eq 1 ]; then
  echo "This appears to be a single-package repository"
  echo "For single-package repos, tag format should be 'vx.y.z' instead of 'packageName@version'"
else
  echo "This appears to be a multi-package repository"
  echo "Current implementation using 'packageName@version' tag format is appropriate"
fi

Length of output: 588

---

Action Required: Update Tag Format for Single-Package Repository

Our repository verification confirms that there is only one package.json file, indicating a single-package repository. In such cases, the tag generated should follow the v<version> format. Please update the tag in src/run.ts (Lines 120-124) accordingly. For example:

-if (!pushAllTags) {
-  await gitUtils.pushTag(
-    `${pkg.packageJson.name}@${pkg.packageJson.version}`,
-  )
-}
+if (!pushAllTags) {
+  await gitUtils.pushTag(`v${pkg.packageJson.version}`)
+}

src/run.ts (1)

154-160: Use Promise.all for better performance when pushing multiple tags.

When pushing multiple tags, using Promise.all would provide better performance by executing the pushes in parallel rather than sequentially.

if (!pushAllTags) {
-  for (const pkg of releasedPackages) {
-    await gitUtils.pushTag(
-      `${pkg.packageJson.name}@${pkg.packageJson.version}`,
-    )
-  }
+  await Promise.all(
+    releasedPackages.map(pkg => 
+      gitUtils.pushTag(`${pkg.packageJson.name}@${pkg.packageJson.version}`)
+    )
+  )
}

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

.github/workflows/pkg-pr-new.yml (1)

30-30: Update publish command with --compact flag

The command now runs as yarn dlx pkg-pr-new publish --compact, which is intended to produce a more concise output during the publish process. Please confirm that:

• The --compact option is recognized by the pkg-pr-new tool.
• The behavior of the publishing step (including any tag pushing logic affected by this flag) remains correct as per the new PR objectives.
• Any documentation updates (e.g., related to INPUT_PUSH_ALL_TAGS and tag handling) are consistent with this change.

Consider running a pipeline test to verify that the new flag does not cause unintended side effects.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro